Is the E2E Enciphering in the settings only for Rclone stored products and not files in any object storage service? There is the principle of encryption is what I download the corresponding to the local is still do not need to enter any decryption password can be opened to use, I am very confused!
E2E encryption is supported for both S3 and Rclone endpoints. For S3 endpoint as on your attached screenshot E2E encryption is enabled correctly and will apply for any NEW files that are uploaded, existing files will remain unencrypted until you reupload them.
For Rclone endpoints E2E needs to be enabled via crypt, please refer to: https://docs.s3drive.app/setup/providers/#other-protocolsproviders
Personal storage compatible with S3, WebDav and 70+ other Rclone back-ends
Tom
E2E encryption is supported for both S3 and Rclone endpoints. For S3 endpoint as on your attached screenshot E2E encryption is enabled correctly and will apply for any NEW files that are uploaded, existing files will remain unencrypted until you reupload them.
For Rclone endpoints E2E needs to be enabled via crypt, please refer to: https://docs.s3drive.app/setup/providers/#other-protocolsproviders
U mean before uploading the files have been encrypted all the time by local E2E encryption ？ But when I try to download my files I don't see any prompt about The step that requires the input of a key to decrypt.I don't need to do any decryption either before downloading or when it's ready to open locally, which is strange. Does this encryption really work on my file data? I don't understand how that works. Please explain!
You don't see prompt when downloading, because it's decrypted automatically by the app, your E2E encryption password is stored inside. If you disable E2E you will then no longer be able to download encrypted files until you turn it on again.
5:58 PM
Describe please your workflow. What you do and what you expect. I am sure lots of context is lost here in the translation.
Easy-to-use client that converts any S3 server into your personal encrypted file storage. Rclone compatible, mount as drive, WebDav server, file versioning.
Easy-to-use client that converts any S3 server into your personal encrypted file storage. Rclone compatible, mount as drive, WebDav server, file versioning.
Basically if you can login to your Huawei S3 bucket through Web: https://web.s3drive.app/ then this would be a confirmation that your CORS settings are set up correctly.
Easy-to-use client that converts any S3 server into your personal encrypted file storage. Rclone compatible, mount as drive, WebDav server, file versioning.
If you know how to set it up yourself, then go ahead. Otherwise please use Settings in the S3Drive.
6:21 PM
We use these settings, if you want to set it up yourself:
<CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<CORSRule>
<ID>S3Drive</ID>
<AllowedOrigin>https://web.s3drive.app</AllowedOrigin>
<AllowedMethod>GET</AllowedMethod>
<AllowedMethod>HEAD</AllowedMethod>
<AllowedMethod>POST</AllowedMethod>
<AllowedMethod>PUT</AllowedMethod>
<AllowedMethod>DELETE</AllowedMethod>
<MaxAgeSeconds>3600</MaxAgeSeconds>
<ExposeHeader>etag</ExposeHeader>
<ExposeHeader>x-amz-meta-x-amz-key</ExposeHeader>
<ExposeHeader>x-amz-meta-x-amz-iv</ExposeHeader>
<ExposeHeader>x-amz-meta-x-amz-cek-alg</ExposeHeader>
<ExposeHeader>x-amz-meta-x-amz-wrap-alg</ExposeHeader>
<ExposeHeader>x-amz-meta-x-amz-key-v2</ExposeHeader>
<ExposeHeader>x-amz-meta-x-amz-tag-len</ExposeHeader>
<ExposeHeader>x-amz-meta-x-amz-unencrypted-content-length</ExposeHeader>
<ExposeHeader>x-amz-version-id</ExposeHeader>
<ExposeHeader>x-amz-meta-key</ExposeHeader>
<ExposeHeader>x-amz-meta-iv</ExposeHeader>
<ExposeHeader>x-amz-meta-chunk</ExposeHeader>
<ExposeHeader>x-amz-meta-cek-alg</ExposeHeader>
<ExposeHeader>x-amz-meta-s3drive</ExposeHeader>
<ExposeHeader>x-amz-meta-mtime</ExposeHeader>
<AllowedHeader>*</AllowedHeader>
</CORSRule>
</CORSConfiguration>
I need to check that, but... actually it maybe mistake on our side. If versioning is disabled, then in fact normal delete is hard delete, because no version existed, so if you delete the files, it's gone.
6:37 PM
We should disable hard delete button if versioning is disabled.
Tom
I need to check that, but... actually it maybe mistake on our side. If versioning is disabled, then in fact normal delete is hard delete, because no version existed, so if you delete the files, it's gone.
2